Release 10.1A: OpenEdge Data Management:
Database Administration

PROUTIL DUMP qualifier

Performs a binary dump of a database table to a file.

proutil db-name -C dump [owner-name.]table-name directory [ -index num ]         {[-thread n ] [-threadnum nthreads] [-dumplist dumpfile] }

Parameters

db-name

Specifies the database where the dump will occur. If the database is not within the current working directory, you need to define the complete path.

owner-name

Specifies the owner of the table containing the data you want to dump. You must specify an owner name unless the table’s name is unique within the database, or the table is owned by PUB. By default, Progress 4GL tables are owned by PUB.

table-name

Specifies the name of the table containing the data you want to dump.

directory

Specifies the name of the target directory where the data will be dumped.

-index num

Specifies the index to use to dump the table’s contents. Word indexes are not allowed. If you choose not to use this option, the command uses the primary index to dump the table.

-thread n

For databases with an Enterprise license, indicate if an online dump is threaded. Specify 0 for a single-threaded dump, 1 for a threaded dump.

-threadnum nthreads

For a threaded dump, specify the maximum number of threads to create. The default value is the number of system CPUs. The actual number of threads created may be less than nthreads. PROUTIL DUMP determines the number of threads to create based on the complexity of the index the DUMP follows.

-dumplist dumpfile

For a threaded dump, create a file, dumpfile, that lists all the files created by the binary dump. dumpfile can be used as an input parameter to binary load.

PROUTIL DUMP writes data from a table to a dump file or files. When the procedure finishes, it reports the number of records written to the dump file. For a threaded dump, the number of records written by each thread is also reported.

Notes

See Chapter 15, "Dumping and Loading," for more information about the DUMP qualifier.
The PROUTIL DUMP and LOAD utilities use cyclic redundancy check (CRC) values to establish the criteria for loading.

The OpenEdge database provides a flexible storage architecture and the ability to relocate objects, such as tables and indexes, while the database remains online. As a result, when you perform a binary load operation, the table numbers in a binary dump file might not match the table numbers in the target database. Therefore, when you perform a binary load operation, the criteria for loading tables is based solely on cyclic redundancy check (CRC) values, and not table numbers.

For example, when you dump a table, the PROUTIL utility calculates a CRC value for the table and stores it in the header of the binary dump file. When you load the table, PROUTIL matches the CRC value stored in the header with the CRC value of the target table. The values must match or the load is rejected.

You can load a binary dump file created with a previous version of the PROUTIL DUMP utility, because the current version of PROUTIL LOAD uses the CRC value established when the file was originally dumped. Consequently, the database maintains backwards compatibility.

PROUTIL DUMP writes data from a table to a dump file or files. The name of the resulting dump files depends on the owner of the table. By default, Progress 4GL tables are owned by PUB. When tables owned by PUB are dumped to a file by an offline or single-threaded online dump, the filename is the table name with .bd appended. For example, tablename.bd.

However, when tables owned by anyone other than PUB are dumped to a file, the resulting filename contains the owner name and table name. For example, ownername_tablename.bd

On systems that have a 2GB-file-size limitation, PROUTIL DUMP creates multiple files when you dump a table larger than 2GB. For example, when you dump data from a table with the name “customer” that is 6.4GB, PROUTIL DUMP creates four binary dump files: customer.bd, customer.bd2, and customer.bd3, each of which is approximately 2GB, and customer.bd4, which is approximately 0.4GB. The PROUTIL DUMP procedure adds header blocks to the binary dump files. As a result, the total size of the binary dump files is slightly larger than the table itself.

On systems without 2GB-file-size limitation, PROUTIL DUMP, running singly threaded, creates only one binary dump file regardless of the size of the table.

For all threaded dumps, PROUTIL DUMP creates multiple files, one for each thread. The first thread creates the file, tablename.bd; the second thread creates the file tablename.bd2; each additional thread creates a file with an incremental number, tablename.bdn. Use the -dumpfile option to generate a list of the files created by the threaded dump.
If the file specified by the -dumpfile option exists, PROUTIL DUMP will overwrite the existing file.
PROUTIL DUMP supports dumping binary large objects (BLOBS).
PROUTIL DUMP does not record the code page of the data it writes to the dump file. Dumped data can only be loaded to a database with the same code page as the source database. Use the ASCII dump and load utilities to perform a code page conversion with your dump and load. For more information on the ASCII utilities, see the "Dumping user table contents with a Data tool" section.